Reservation of resources and deployment of applications using an integrated development environment

ABSTRACT

Systems and methods to reserve resources is provided. In exemplary embodiments, a selection of a profile from a user is received. A dynamic graphical user interface is generated, using one or more processors. The dynamic graphical user interface allows the user to configure a topology based on the selected profile. The dynamic graphical user interface provides input fields in which the user may select a resource. An indication of the selected applicable topology property for configuring the topology is received. A topology is automatically generating based in part on the selected applicable topology property.

PRIORITY

This application is a continuation of U.S. patent application Ser. No.16/021,756, filed Jun. 28, 2018, which is a continuation of U.S. patentapplication Ser. No. 15/051,238, filed Feb. 23, 2016, now issued as U.S.Pat. No. 10,044,639, which is a continuation of U.S. patent applicationSer. No. 13/931,389, filed on Jun. 28, 2013, now issued as U.S. Pat. No.9,282,009, which is a continuation of U.S. patent application Ser. No.12/855,650, filed Aug. 12, 2010, now issued as U.S. Pat. No. 8,479,098,which is a continuation of U.S. patent application Ser. No. 12/855,644,filed on Aug. 12, 2010, now issued as U.S. Pat. No. 8,635,534, whichclaims the benefit of U.S. Provisional Patent Application Ser. No.61/233,425, filed on Aug. 12, 2009, the benefit of priority of each ofwhich is claimed hereby, and each of which are incorporated by referenceherein in their entirety.

FIELD

The present disclosure relates generally to networking, and in aspecific example embodiment, to reservations of resources and deploymentof applications in a network.

BACKGROUND

Cloud computing is a form of distributed computing in which computingresources are provided as a service over a network. In particular, acloud is a computing architecture characterized by a number ofinterconnected machines (e.g., computing devices such as personalcomputers, servers, routers, and load balancers). Conventionally,resource allocation in a cloud computing environment is based on typesof architecture specific to particular models. That is, thearchitectures are typically hardcoded to specific models or plans. Whilethis hardcoding provides a simple mechanism for reserving allocatedresources, it does not allow any flexibility in the system.Additionally, more complex allocation schemes (e.g., pool creation) maytake an extraordinary amount of time (e.g. two months) and a largeamount of trace tickets (e.g., 100 trace tickets). Thus, resourceallocation using conventional systems is time consuming and requires asignificant investment in human resources.

BRIEF DESCRIPTION OF THE DRAWINGS

Various ones of the appended drawings merely illustrate exampleembodiments of the present invention and cannot be considered aslimiting its scope.

FIG. 1 is a block diagram illustrating an example of an environment inwhich example embodiments may be deployed.

FIG. 2 is a block diagram illustrating an example embodiment of acomputing device.

FIG. 3 is a flowchart of an example method for reserving resources anddeployment of applications.

FIG. 4 is an example of a portion of a graphical user interface forselecting a profile.

FIG. 5 is an example of a portion of a graphical user interface forsetting topology properties.

FIG. 6 is an example of a portion of a graphical user interface forgraphically monitoring the deployment of an application.

FIG. 7 is a simplified block diagram of a machine in an example form ofa computing system within which a set of instructions for causing themachine to perform any one or more of the methodologies discussed hereinmay be executed.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the present invention. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques have not been shown in detail.

As used herein, the term “or” may be construed in either an inclusive orexclusive sense. Additionally, although various example embodimentsdiscussed below focus on a specific network-based environment, theembodiments are given merely for clarity in disclosure. Thus, any typeof electronic commerce or electronic business systems, including varioussystem architectures, may employ various embodiments of the managementsystem described herein and is considered as being within a scope ofexample embodiments. Each of a variety of example embodiments isdiscussed in detail, below.

Embodiments of the present invention provide systems and methods toreserve resources in a network. In one embodiment, the network is acloud environment. In exemplary embodiments, a selection of a profilerelated to a project is received from a user. The profile may beselected from a list of available profiles. A dynamic graphical userinterface is generated, using one or more processors. The dynamicgraphical user interface allows the user to configure a topology basedon the selected profile. The graphical user interface provides inputfields in which the user may select an applicable topology property. Anindication of the selected applicable topology property for configuringthe topology is received. The topology may be automatically generatedbased in part on a submission of the selected applicable topologyproperty.

With reference to FIG. 1, an embodiment of a cloud computing environment100 in which example embodiments of the present invention may bedeployed is shown. The cloud computing environment 100 depicts acomputing device 102 configured to host an integrated developmentenvironment 104. The computing device 102 is communicatively coupled toone or more clouds 106. For example, the computing device 102 may becoupled via a network (e.g., WAN, LAN, Internet) to the cloud 106. It isnoted that while example embodiments discuss cloud computing,embodiments of the present invention may applied to any type ofcomputing environment.

The cloud 106 may comprise a plurality of devices 108 or components(collectively referred to as resources) such as, for example, one ormore of a server, pool, service, complete site, or any other componentsor collection of components that may be reserved and monitored by thecomputing device 102. In some embodiments, the cloud 106 may furthercomprise a cloud management system 110 that dynamically managesresources and deploys applications within the cloud 106. In oneembodiment, the cloud management system 110 may be embodied within thecomputing device 102. The cloud may also comprise one or more virtualmachines 112.

In example embodiments, the integrated development environment 104provides tools for software development in a variety of differentprogramming languages, such as JAVA, C++, and JavaScript. Examples oftools include source code editors, compilers, interpreters, buildautomation tools, and debuggers. Additionally, in accordance withembodiments of the present invention, the integrated developmentenvironment 104 may facilitate virtualization of an application acrossthe cloud 106. In particular, the integrated development environment 104can accept and accommodate plug-in tools that facilitate the deploymentof applications in the cloud computing environment 100. For example, auser can develop an application (e.g., project) using the integrateddevelopment environment 104. After the application is developed, theintegrated development environment 104 facilitates reservation ofresources in the cloud 106 for the deployment of the application. Forexample, a number of devices 108 may be reserved to execute theapplication. As discussed further below, the integrated developmentenvironment 104 further provides dynamically generated graphically userinterfaces (GUIs) to develop the application, initiate reservation ofthe resources, and monitor deployment of the application.

FIG. 2 is a block diagram illustrating an example embodiment of thecomputing system 102. The computing device 102 may be deployed using,for example, a personal computer, a laptop computer, a server computer,a tablet personal computer, or any other type of computing device. Thecomputing device 102 may be used to implement computer programs, logic,applications, methods, processes, or software that, in turn, developapplications, reserve resources, deploy the applications, and monitorthe deployment as is described in more detail below.

In example embodiments, the computing device 102 executes an operatingsystem 202 that manages the hardware on the computing device 102 toexecute processes or services. These processes or services include theintegrated development environment 104. The integrated developmentenvironment 104 may comprise or access a variety of differentapplications and plug-ins. In one embodiment, the integrated developmentenvironment 104 comprises a project wizard module 204, a graphics module206, a deployment module 208, and a monitoring module 210communicatively coupled together. In some embodiments, the functions ofone or more of the modules (e.g., the graphics module 206) may beincorporated into the project wizard module 204.

The project wizard module 204 allows a user to create a project orapplication, which may be deployed on the network or cloud. Inaccordance with one embodiment, the project wizard module 204 accessesinformation models, such as profiles (e.g., predefined templates ofparticular resources) in a configuration repository (not shown) based onthe application the user desires to create. Profiles may span bothinfrastructure and platform. Each profile may be a generic specificationfor a project or application in a given architecture domain (e.g., V3,service oriented architecture (SOA), messaging) for providing a desiredservice. The profile may specify entities, resource types, or componentsthat the project associated with the profile requires (e.g., applicationservers, switch, load balancer), the profile's cardinalities,configuration parameters, and inter-relationships. Thus, the profileindicates, generically, which resources or components, and connectionsmade between those components, are used to implement a particularservice (e.g., application).

The project wizard module 204 works in conjunction with the graphicsmodule 206 to provide the user with dynamic GUIs that allow the user tocreate the project. When the user selects a profile for the project viathe project wizard module 204, the graphics module 212 generates adynamic GUI for configuring a topology based on the selected profile.Specifically, the dynamic GUI allows for selection of topologyproperties (e.g., resources) that will be used by the selected projectonce deployed. In some embodiments, some of the properties may bedefault or set by the project wizard module 204 based on the profile.The defaults may be changeable by the user. In other embodiments, theproperties may be selected from a drop-down menu, a checkbox, or bemanually entered by the user. Because the GUI is generated based on aspecific profile and on applicable topology properties (which maychange), the GUI is dynamic and may be different in each instantiation.

During the selection of topology properties (e.g., resources), adetermination may be made whether a particular property or resource isapplicable. In one embodiment, the project wizard module 204 may use aset of algorithms and policies that are applied prior to allowingselection of resource topology property. The policies may comprise a setof fault domain standards that apply to a selected topology property(e.g., machine). For instance, the fault domain standard may assure thatif the particular resource fails, the failure will not affect an entirepool but only a limited number of resources. Other examples of policiesinclude, for example, if the particular resource is a virtual machine,the virtual machine cannot be on the same DeX server or particularresources cannot be chosen if they are physically located on the samerack, chassis, power grid, or data center. Thus, the policies and faultdomain standards operate to increase reliability for a project (e.g.,application or service). It should be noted that a similar applicationof algorithms and policies may be utilized in reserving the individualor specific resources (e.g., the actual machine or device) that will beneeded in deployment of the application.

In another example, the project may require a load balancer having highcapacity. If a particular load balancer does not have enough capacity,the GUI provided by the graphics module 206 does not allow the user toselect that load balancer. In some embodiments, the project wizardmodule 204, via the GUI, may dynamically determine and suggest otherresources. Thus, the dynamic GUI limits the user to resources that areavailable, match the capabilities and requirements of the selectedprofile, and comply with policies (e.g., fault domain standards).

Once all the topology properties are selected and received by theproject wizard module 204, a topology for the project is generated bythe project wizard module 204. The topology is a realization of theprofile which specifies actual resources and number of resources thatare used to provide the service (e.g., the project). In variousembodiments, the topology may be logical or physical. The logicaltopology specifies abstract resources (e.g., two servers, one switch,and one load balancer) while the physical topology specifies concreteresources (e.g., two LS20 servers, one Cisco 3550 switch, and oneNetScaler load balancer). As such, the physical topology may ultimatelybe used for project deployment.

The topology represents a graph of resources and relationships betweenthese resources. Each node in the topology represents a different phasein an implementation of the project described by the topology, and theorchestration of the topology is based on relationships between thesenodes. When a topology is created, the topology represents the projectand indicates the resources required to implement the project. Thetopology may not necessarily indicate the actual devices 108, but mayleave the selection of the actual devices 108 to the cloud managementsystem 110 or other provisioning system.

For example, a particular project for processing requests may requirethat a pool of devices 108 includes devices 108 located in multiple datacenters that, in turn, have load balancers that are configured to loadbalance a request. Further, the request is serviced by some machine inthe pool that is configured to access a database. The topology, in thisexample, represents a whole graph of these resources (e.g., machine,load balancer, database) and how these resources connect to each other.

The project wizard module 204 then reserves or provides instruction toother components (e.g., the cloud management system 110 or provisioningsystem) to reserve resources for the generated template. The reservationof resources may comprise identifying the individual resources (e.g.,devices 108) that will be deployed by the application represented by thetopology. In some embodiments, the reservation of resources may comprisea pre-provisioning of the individual resources.

The deployment module 208 (e.g., a cloud server module) deploys theapplication upon initiation by the user. For example, the deploymentmodule 208 may create a Directed Acyclic Graph (DAG) or other types ofgraphs which specifies the tasks to be performed in order to deploy theapplication. The DAG is then traversed by the deployment module 208 inorder to determine an order in which to execute nodes of the DAG (e.g.,tasks) of the DAG. In some cases, the nodes of the DAG represent thereserved resources.

The DAG is generated based on the topology and rules accessed from arules database. The rules may be based on observations. Relationshipsand dependencies between and within resources in the cloud computingenvironment 100 are based on standards (e.g., TCP/IP and other relevantstandards) or are readily apparent. For example, a web applicationcannot be deployed without a server, or a load balancer cannot loadbalance if it does not have an IP address. Thus, parent-childrelationships may exist (e.g., one thing needs to occur before another).All of these relationships can be used to create task precedence rules.As a result, the structure of the DAG or orchestration plan can beinferred from the topology based on these rules. By generating the DAG,individual orchestration plans do not need to be hard-coded resulting insignificantly reduced development time and errors. Thus, the actualdeployment of an application is conducted according to a graph traversalalgorithm whereby an order to perform the nodes in the DAG is determinedand executed. Upon completion of the execution of the nodes in the DAG,the application is fully deployed.

During deployment, the monitoring module 210 may monitor the progress ofthe deployment (e.g., execution of the nodes in the DAG) and instructthe graphics module 206 to illustrate the progress to the user.Specifically, a graphics module 206 generates a GUI illustrating the DAGfor deployment of the application. A status indicator may also beassociated with each node of the DAG such that the user may visuallyobserve the progress of the execution of the node. Thus, the applicationdeployment process is monitored in real-time by the monitoring module210.

Referring now to FIG. 3, a flowchart of an example method 300 forreserving resources and deployment of an application in a cloudcomputing environment (e.g., cloud computing environment 100) is shown.In operation 302, a selection of a profile is received by the projectwizard module 204. In some embodiments, a user associated with thecomputing device 102 logs into the integrated development environment104 and verifies eligibility for creating a new cloud project (e.g.,application). The user then selects a profile (e.g., project template).The user may also provide a name for the new project and a name for thetopology that will be generated for the project. The profile is accessedby the project wizard module 204 for processing.

In operation 304, a topology property setup page (e.g., a GUI forconfiguring a topology based on the selected profile) is dynamicallygenerated based on the selected profile. The graphics module 206generates the setup page based on data received from the project wizardmodule 204 and provides the setup page to the user. The setup page mayprovide input fields (e.g., manual entry boxes, drop-down menus,checkboxes) that allow the user to configure properties of the projectsuch that a customized topology can be created from the profile.

During the selection of topology properties (e.g., resources), adetermination may be made whether a particular topology property (e.g.,resource) is applicable based on algorithms and policies (e.g., a set offault domain standards). If a particular topology property is notapplicable or available, the GUI provided by the graphics module 206does not allow the user to select that topology property. In someembodiments, the project wizard module 204 via the GUI may dynamicallyselect or suggest other properties. Thus, the dynamic GUI may limit theuser to properties that are available, match the capabilities andrequirements of the selected profile, and comply with policies (e.g.,fault domain standards). The selection of the resources effectivelyreserves the resources for deployment in accordance with one embodiment.

For example, the profile may specify that a load balancer, anapplication tier, and a database are required. The setup page allows theuser to select a type of load balancer (e.g., NetScaler or F5), a typeof login service (e.g., CAL), and database (e.g., MySql, Oracle) viainput fields. Some of the input fields may be default, which can bechanged by the user. Other input fields may require the user to selectfrom a drop-down menu or manually enter a value.

Once the setup page is completed (e.g., all desired topology propertiesare inputted) and submitted, the customized topology is generated inoperation 306. In example embodiments, the project wizard module 204generates the topology. As discussed, the topology comprises a plan fordeployment represented as a graph of resources and their relationshipswith each other.

In operation 308, resources corresponding to the generated topology arereserved. In example embodiments, the reservation of resources isperformed upon the creation and saving of the topology. In oneembodiment, the project wizard module 204 may reserve or providesinstructions to other components (e.g., the cloud management system 110or provisioning system) to reserve resources for the generated template.The reservation of resources may comprise, in one embodiment,identifying the individual and actual resources (e.g., devices 108) thatwill be deployed by the application represented by the topology. In someembodiments, the reservation of resources may comprise apre-provisioning of the individual resources.

As a result, the reservation of resources facilitates reserving oraccessing technology-enabled services via the integrate developmentenvironment 104 without, for example, knowledge of, expertise with, orcontrol over the technology infrastructure that supports theapplication. For instance, the automation of the resource reservationmay allow a user without detailed knowledge of the physical aspects ofthe cloud (e.g., Internet Protocol (IP) address) to reserve resources.

In operation 310, the application may be deployed. The deployment module208 deploys the application upon receiving an indication from the user.For example, the deployment module 208 may create a Directed AcyclicGraph (DAG) which illustrates tasks that need to be performed in orderto deploy the application. The DAG is then traversed in order todetermine an order in which to execute nodes (e.g., tasks) of the DAG.The nodes are then executed in the determined order.

In one embodiment, the deployment module 208 may transmit a command tothe cloud management system 110 to deploy the application. Thedeployment may be phased where, for example, the deployment module 208may specify the deployment of a portion of the application.Alternatively, the deployment may be complete where, for example,deployment module 208 may specify the deployment of the completeapplication. Additionally, the deployment module 208 may also trigger arollback (e.g., remove the deployed application from the cloud) of thedeployed application.

During deployment, the progress of the deployment (e.g., execution ofthe nodes in the DAG) may be monitored in operation 312 by the monitormodule 210. The monitor module 210 may instruct the graphics module 206to illustrate the progress to the user. Specifically, the graphicsmodule 206 generates a GUI illustrating the DAG for deployment of theapplication. A status indicator may also be associated with each node ofthe DA such that the user may visually observe the progress of theexecution of the node. Thus, the application deployment process ismonitored in real-time by the monitoring module 210. Thus, theapplication deployment process is monitored in real-time and providedgraphically to the user.

FIG. 4 is an example of a portion of a graphical user interface forselecting a profile. In the example of FIG. 4, only a single profile isshown available for selection. However, alternative examples maycomprise any number of profiles from which the user may select. Uponselection of profile, the user may be asked to name the new project andnew topology (e.g., My Topology) if one is to be created.

FIG. 5 is an example of a portion of a graphical user interface forsetting topology properties (e.g., selecting resources). Upon selectionof the profile, the project wizard module 204 accesses the profile anduses the information for the profile to instruct the graphics module 212to generate the graphical user interface. Thus, the graphical userinterface is specific to the selected profile (e.g., input fields arecustomized based on the profile). Some of the input fields in thegraphical user interface may be pre-populated or filled with a defaultvalue. For example, the topology name may be pre-populated with a namepreviously provided. Other input fields may be selected or populated bythe user. For example, the user may decide to use a database, to use CALas a login service, and to use Tomcat 6.0 of a servlet container.

It should be noted that not all input fields require an input. Forexample, if the user decides not to use a database, a database detailsection 502 may be greyed out or the user is otherwise not able toprovide any inputs into the database detail section 502. Once thetopology properties are selected and submitted, the topology isgenerated and the resources reserved.

FIG. 6 is an example of a portion of a graphical user interface (GUI)for graphically monitoring the deployment of an application in realtime. In the present example, the topology requires a load balancer andtwo servers. Thus, the GUI illustrates a Directed Acyclic Graph (DAG)602 comprising a load balancer node 604 and two server nodes 606 and608.

The deployment of an application is a graph traversal algorithm. Forexample, in order to deploy the load balancer, the two servers must bedeployed. As shown in the example of FIG. 6, a first server is deployed(as shown by a progress bar 609) and the second server is being deployed(as shown by a progress bar 610). Once the second server is deployed,the load balancer may then be deployed. Upon completion of deployment ofthe load balancer, the application is fully deployed.

The GUI for monitoring deployment may further comprise a table (notshown) of a job number of the deployment, task identifiers, tasks (e.g.,deploy serverapp1, deploy serverapp2), status of the deployment (e.g.,completed, in-_flight), results of the deployment (e.g., success,unknown), and percent of deployment completed (e.g., 100%). Thus, theuser may monitoring the deployment of the application in real-time.

Modules, Components, and Logic

Certain embodiments described herein may be implemented as logic or anumber of modules, engines, components, or mechanisms. A module, engine,logic, component, or mechanism (collectively referred to as a “module”)may be a tangible unit capable of performing certain operations andconfigured or arranged in a certain manner. In certain exemplaryembodiments, one or more computer systems (e.g., a standalone, client,or server computer system) or one or more components of a computersystem (e.g., a processor or a group of processors) may be configured bysoftware (e.g., an application or application portion) or firmware (notethat software and firmware can generally be used interchangeably hereinas is known by a skilled artisan) as a module that operates to performcertain operations described herein.

In various embodiments, a module may be implemented mechanically orelectronically. For example, a module may comprise dedicated circuitryor logic that is permanently configured (e.g., within a special-purposeprocessor, application specific integrated circuit (ASIC), or array) toperform certain operations. A module may also comprise programmablelogic or circuitry (e.g., as encompassed within a general-purposeprocessor or other programmable processor) that is temporarilyconfigured by software or firmware to perform certain operations. Itwill be appreciated that a decision to implement a module mechanically,in the dedicated and permanently configured circuitry, or in temporarilyconfigured circuitry (e.g., configured by software) may be driven by,for example, cost, time, energy-usage, and package size considerations.

Accordingly, the term module should be understood to encompass atangible entity, be that an entity that is physically constructed,permanently configured (e.g., hardwired), or temporarily configured(e.g., programmed) to operate in a certain manner or to perform certainoperations described herein. Considering embodiments in which modules orcomponents are temporarily configured (e.g., programmed), each of themodules or components need not be configured or instantiated at any oneinstance in time. For example, where the modules or components comprisea general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differentmodules at different times. Software may accordingly configure theprocessor to constitute a particular module at one instance of time andto constitute a different module at a different instance of time.

Modules can provide information to, and receive information from, othermodules. Accordingly, the described modules may be regarded as beingcommunicatively coupled. Where multiples of such modules existcontemporaneously, communications may be achieved through signaltransmission (e.g., over appropriate circuits and buses) that connectthe modules. In embodiments in which multiple modules are configured orinstantiated at different times, communications between such modules maybe achieved, for example, through the storage and retrieval ofinformation in memory structures to which the multiple modules haveaccess. For example, one module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further module may then, at a later time,access the memory device to retrieve and process the stored output.Modules may also initiate communications with input or output devicesand can operate on a resource (e.g., a collection of information).

Example Machine Architecture and Machine-Readable Medium

With reference to FIG. 7, an exemplary embodiment extends to a machinein the exemplary form of a computer system 700 within which instructionsfor causing the machine to perform any one or more of the methodologiesdiscussed herein may be executed. In alternative exemplary embodiments,the machine operates as a standalone device or may be connected (e.g.,networked) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client machine in server-clientnetwork environment, or as a peer machine in a peer-to-peer (ordistributed) network environment. The machine may be a personal computer(PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant(PDA), a cellular telephone, a web appliance, a network router, a switchor bridge, or any machine capable of executing instructions (sequentialor otherwise) that specify actions to be taken by that machine. Further,while only a single machine is illustrated, the term “machine” shallalso be taken to include any collection of machines that individually orjointly execute a set (or multiple sets) of instructions to perform anyone or more of the methodologies discussed herein.

The exemplary computer system 700 may include a processor 702 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU) orboth), a main memory 704 and a static memory 706, which communicate witheach other via a bus 708. The computer system 700 may further include avideo display unit 710 (e.g., a liquid crystal display (LCD) or acathode ray tube (CRT)). In exemplary embodiments, the computer system700 also includes one or more of an alpha-numeric input device 712(e.g., a keyboard), a user interface (UI) navigation device or cursorcontrol device 714 (e.g., a mouse), a touchscreen (not shown), a diskdrive unit 716, a signal generation device 718 (e.g., a speaker), and anetwork interface device 720.

Machine-Readable Medium

The disk drive unit 716 includes a machine-readable medium 722 on whichis stored one or more sets of instructions 724 and data structures(e.g., software instructions) embodying or used by any one or more ofthe methodologies or functions described herein. The instructions 724may also reside, completely or at least partially, within the mainmemory 704 or within the processor 702 during execution thereof by thecomputer system 700, the main memory 704 and the processor 702 alsoconstituting machine-readable media.

While the machine-readable medium 722 is shown in an exemplaryembodiment to be a single medium, the term “machine-readable medium” mayinclude a single medium or multiple media (e.g., a centralized ordistributed database, or associated caches and servers) that store theone or more instructions. The term “machine-readable medium” shall alsobe taken to include any tangible medium that is capable of storing,encoding, or carrying instructions for execution by the machine and thatcause the machine to perform any one or more of the methodologies ofembodiments of the present invention, or that is capable of storing,encoding, or carrying data structures used by or associated with suchinstructions. The term “machine-readable medium” shall accordingly betaken to include, but not be limited to, solid-state memories andoptical and magnetic media. Specific examples of machine-readable mediainclude non-volatile memory, including by way of exemplary semiconductormemory devices (e.g., Erasable Programmable Read-Only Memory (EPROM),Electrically Erasable Programmable Read-Only Memory (EEPROM), and flashmemory devices); magnetic disks such as internal hard disks andremovable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks.The machine-readable medium may also comprise non-transitorymachine-readable medium.

Transmission Medium

The instructions 724 may further be transmitted or received over acommunications network 726 using a transmission medium via the networkinterface device 720 and utilizing any one of a number of well-knowntransfer protocols (e.g., HTTP). Examples of communication networksinclude a local area network (LAN), a wide area network (WAN), theInternet, mobile telephone networks, Plain Old Telephone (POTS)networks, and wireless data networks (e.g., WiFi and WiMax networks).The term “transmission medium” shall be taken to include any intangiblemedium that is capable of storing, encoding, or carrying instructionsfor execution by the machine, and includes digital or analogcommunications signals or other intangible medium to facilitatecommunication of such software.

Although an overview of the inventive subject matter has been describedwith reference to specific exemplary embodiments, various modificationsand changes may be made to these embodiments without departing from thebroader spirit and scope of embodiments of the present invention. Suchembodiments of the inventive subject matter may be referred to herein,individually or collectively, by the term “invention” merely forconvenience and without intending to voluntarily limit the scope of thisapplication to any single invention or inventive concept if more thanone is, in fact, disclosed.

The embodiments illustrated herein are described in sufficient detail toenable those skilled in the art to practice the teachings disclosed.Other embodiments may be used and derived therefrom, such thatstructural and logical substitutions and changes may be made withoutdeparting from the scope of this disclosure. The Detailed Description,therefore, is not to be taken in a limiting sense, and the scope ofvarious embodiments is defined only by the appended claims, along withthe full range of equivalents to which such claims are entitled.

Moreover, plural instances may be provided for resources, operations, orstructures described herein as a single instance. Additionally,boundaries between various resources, operations, modules, engines, anddata stores are somewhat arbitrary, and particular operations areillustrated in a context of specific illustrative configurations. Otherallocations of functionality are envisioned and may fall within a scopeof various embodiments of the present invention. In general, structuresand functionality presented as separate resources in the exampleconfigurations may be implemented as a combined structure or resource.Similarly, structures and functionality presented as a single resourcemay be implemented as separate resources. These and other variations,modifications, additions, and improvements fall within a scope ofembodiments of the present invention as represented by the appendedclaims. The specification and drawings are, accordingly, to be regardedin an illustrative rather than a restrictive sense.

What is claimed is:
 1. A method of managing deployment of a cloudcomputing resource from a cloud management system in the cloud, themethod comprising: receiving, by one or more hardware processors, aconfiguration associated with a first computing resource in the cloudfrom a user interface displaying hardware topology information;receiving a selection of a component associated with the first computingresource in the cloud; determining a first task to deploy the componentto the first computing resource in the cloud; transmitting a command todeploy the component to the first computing resource in the cloud; andcausing presentation of a display of a progress of the deployment of thecomponent to the first computing resource, the display of the progressof the deployment comprises a first status associated with thedeployment on the first computing resource in the cloud.
 2. The methodof claim 1, wherein the display of the progress of the deployment of thecomponent further comprises: a second status associated with deploymenton a second computing resource in the cloud.
 3. The method of claim 1,wherein the display of the progress of the deployment of the componentcomprises a table that provides status of the deployment of thecomponent.
 4. The method of claim 1, further comprising: receiving aproject name for the hardware topology.
 5. The method of claim 1,further comprising: triggering a rollback of the deployment.
 6. Themethod of claim 1, further comprising: monitoring the progress of thedeployment.
 7. The method of claim 1, further comprising: generating agraph used to determine an order associated with the deployment.
 8. Asystem of managing deployment of a cloud computing resource from a cloudmanagement system in the cloud, the system comprising: one or morehardware processors; and a memory storing instructions that whenexecuted by the one or more hardware processors, cause the one or morehardware processors to perform operations comprising: receiving aconfiguration associated with a first computing resource in the cloudfrom a user interface displaying hardware topology information;receiving a selection of a component associated with the first computingresource in the cloud; determining a first task to deploy the componentto the first computing resource in the cloud; transmitting a command todeploy the component to the first computing resource in the cloud; andcausing presentation of a display of a progress of the deployment of thecomponent to the first computing resource, the display of the progressof the deployment comprises a first status associated with thedeployment on the first computing resource in the cloud.
 9. The systemof claim 8, wherein the display of the progress of the deployment of thecomponent further comprises: a second status associated with deploymenton a second computing resource in the cloud.
 10. The system of claim 8,wherein the display of the progress of the deployment of the componentcomprises a table that provides status of the deployment of thecomponent.
 11. The system of claim 8, wherein the operations furthercomprise: receiving a project name for the hardware topology.
 12. Thesystem of claim 8, wherein the operations further comprise: triggering arollback of the deployment.
 13. The system of claim 8, wherein theoperations further comprise: monitoring the progress of the deployment.14. The system of claim 8, wherein the operations further comprise:generating a graph used to determine an order associated with thedeployment.
 15. A non-transitory machine-readable medium storinginstructions that when executed by one or more hardware processors of amachine, cause the machine to perform operations comprising: receiving aconfiguration associated with a first computing resource in the cloudfrom a user interface displaying hardware topology information;receiving a selection of a component associated with the first computingresource in the cloud; determining a first task to deploy the componentto the first computing resource in the cloud; transmitting a command todeploy the component to the first computing resource in the cloud; andcausing presentation of a display of a progress of the deployment of thecomponent to the first computing resource, the display of the progressof the deployment comprises a first status associated with thedeployment on the first computing resource in the cloud.
 16. Thenon-transitory machine-readable medium of claim 15, wherein the displayof the progress of the deployment of the component further comprises: asecond status associated with deployment on a second computing resourcein the cloud.
 17. The non-transitory machine-readable medium of claim15, wherein the display of the progress of the deployment of thecomponent comprises a table that provides status of the deployment ofthe component.
 18. The non-transitory machine-readable medium of claim15, wherein the operations further comprise: triggering a rollback ofthe deployment.
 19. The non-transitory machine-readable medium of claim15, wherein the operations further comprise: monitoring the progress ofthe deployment.
 20. The non-transitory machine-readable medium of claim15, wherein the operations further comprise: generating a graph used todetermine an order associated with the deployment.